Designing Pega for the enterprise
2 Tasks
1 hr
Scenario
You are meeting with the Enterprise Architecture team to discuss the architectural landscape at MDC and how the Delivery Service application fits into it. The following topics will be covered:
- Application access
- Application server technology
- Integration and web services
- Data storage and warehousing
Application access
MDC plans to enable prospective customers to register business partners and truck vendors from a cloud-based web portal. Business partners can initiate delivery requests through a chat interaction or a dedicated user portal. City Managers can track all open truck requests (pickup, delivery, etc.) and follow up with truck vendors using a mobile application. Delivery Service application details must be available offline because City Managers travel frequently. MDC uses an open-source SAML single sign-on (SSO) or Open Identity providers package for user access to all applications.
Application server technology
MDC deploys an enterprise archive on its application servers for all web applications.
Integration and web services
Global Truck Rating Services (GTRS) provides REST services to access truck ratings. MDC requires the truck rating during Truck Vendor registration, and the truck rating service request/response is in JSON format. MDC secures all contact and payment information for Business Partners and Truck Vendors through secure services.
Data storage and reporting
MDC stores and reports historical delivery, truck request, and invoice information in a data warehouse. The new Delivery Service application feeds the warehouse for executive reporting, and warehouse reports are accessible from the Pega application.
Produce a high-level architecture diagram and describe each application component. Use Visio, PowerPoint, Image, or hand-draw your diagram. Assume an on-premises deployment.
In the diagram, illustrate the:
- Components of the application, including web services and the components of the Delivery Service application
- Relationship between Delivery Service application architectural components
- Integration with the Global Truck Rating System (GTRS)
- Integration with the Datawarehouse system
As an alternative solution, describe any differences in design choices for the same set of Pega Cloud requirements.
The following table provides the credentials you need to log in to the Delivery Service application. However, this challenge is mainly meant for evaluating the design options, and there are no specific implementation tasks.
| Role | User name | Password |
|---|---|---|
| Admin | admin@deliveryservice | rules |
Detailed Tasks
1 Identify design options
Any options allowed in the Pega Platform™ support guide are valid. For more information, see the Platform Support Guide.
2 Consider alternative approaches
If the application is deployed on Pega Cloud™ instead of on-premises, you must also consider:
- Pega Cloud services networking – Work with the Pega Cloud team to configure the application to access secured Front Stage resources.
- Integrating Pega applications in Pega Cloud with external systems – Review options available in Pega Cloud.
- Pega Cloud Security Overview – Examples include whitelisting and data residency.
- Business Intelligence Exchange (BIX) for Pega Cloud applications – Pega Cloud uses a separate node for BIX processing.
Confirm your work
Available in the following mission:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?